home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power Tools 1993 November - Disc 2
/
Power Tools Plus (Disc 2 of 2)(November 1993)(HP).iso
/
hotlines
/
cnhl
/
wc
/
gal.cpy
/
SCRIPT.TXT
next >
Wrap
Text File
|
1993-08-17
|
27KB
|
667 lines
Slide 1: HP Windows Client Model 425SX
The Windows Client Model 425SX is the first in a whole new
family of products from HP. Designed to complement HP's
terminal, Unix, and DOS desktop offerings, the Windows Client
family will fill a strongly emerging need combining the
attributes of many of today's desktop alternatives. In the
next 30 minutes, we'll examine the demands that led to the
development of the Windows Client, the Windows Client product
attributes, and examples of the benefits of the Windows
Client from both a user and system perspective.
*************************************************************
Slide 2: The Merging of Two Worlds
As you may know, Hewlett Packard is one of the leading
terminal manufacturers in the world. From this perspective,
we have seen many customers wanting to add a Windows type of
graphical user interface (GUI) and PC applications to their
mission critical environment. These customers are typically
running a traditional host/terminal environment. Our
experience has been that many of these customers have been
reluctant to move to PCs to meet this need because of the
inherent cost or because of concerns over potential loss a
control and manageability that typically comes with PCs.
Still others have paid the expense of a fully functional PC
when they didn't really need all of the capability and
expandability.
At the same time, we have observed an increasing demand from
the MIS community for the ability to more effectively manage
their PC environments.
*************************************************************
Slide 3: The Best of Both Worlds
The HP Windows Client solution brings the best of these two
worlds together into one client platform.
The best of the terminal world gives access to the host based
application while providing centralized systems management,
high data integrity, and security all at a cost per seat that
the PC can't match.
The best of the PC world adds the advantages of Windows
functionality. With this users can run multiple applications
all with the same look and feel. It also brings the
advantages of LAN connectivity, including the ability to
access applications distributed across multiple hosts. Add
to this access to PC software and the power to run
client/server applications and you've got set of capabilities
not possible with a terminal.
The new Windows Client from HP takes the best of each of
these worlds and combines them into a totally new class of
client for client/server systems.
*************************************************************
Slide 4: Introducing the HP Windows Client Model 425SX
The HP Windows Client is a powerful Intel based DOS/Windows
PC designed to function in a LAN environment with a server-
based hard disk. This slide shows an overview of the
hardware and software characteristics.
The heart of the Windows Client is 25 MHz 486 and 4Mb of RAM
to provide the foundation for Windows environment. The RAM
is expandable up to 36 Mb.
The integrated local bus video supports up to 1024 X 768
resolution at 70 Hz refresh rate. Other resolutions allow
even higher 72 Hz refresh rate. Text acceleration is built
into the video subsystem through the implementation of color
expansion. By controlling text color with one bit instead of
sending eight bits for each text pixel, text processing can
be improved by up to 8X. In some cases, text acceleration
can out perform graphics acceleration which is more expensive
to implement.
Another integrated performance feature is the bus mastering
16-bit LAN interface. This allows the network to communicate
directly with the Windows Client memory without performing a
CPU interrupt. This keeps the CPU efficiency at a maximum.
Additional features and components of the Windows Client
package include a serial and parallel interface, keyboard,
and mouse.
The software licenses included with each Windows Client
really enhance the total solution value. Each Windows Client
ships with a license to use Microsoft DOS 6.0, Windows 3.1,
and a full suite of software from Walker Richer & Quinn.
Reflection Network Series (RNS) provides support for a wide
variety of network protocols while Reflection 1 for Windows
and Reflection 2 for Windows provide terminal emulation for
HP block mode and DEC VT220 and VT320 mode.
Combined, the total list price value of the software comes to
over $1,000.
There are five monitor choices available to fit a range of
application and video needs including monochrome VGA, color
VGA, Super VGA, Ergonomic Super VGA, and Ergonomic Ultra VGA
with a 15 inch screen. There is also one configuration with
no monitor in the event that different video solution is
required.
The six Windows Client configurations available start from
just $895 list price up to $1,675. This is up to 40% lower
than comparably configured networked PCs and represents true
breakthrough pricing for a fully configured DOS/Windows
client solution including software.
The Windows Client employs a low cost focused design targeted
for transaction oriented environments moving up from a
terminal platform. All required interfaces, including video
and LAN, are integrated, so there are no additional I/O slots
provided. Since the Windows Client uses server-based disks,
there is no integrated mass storage capability.
*************************************************************
Slide 5: Powerful Windowing Environment
All of these attributes of the Windows Client combine to
create a powerful window into the network. Users can run
multiple terminal emulations on different hosts while
simultaneously running PC and client/server applications.
Bundled in with the Windows Client are block mode and VT
terminal emulators from WRQ. Others are available through
third parties, including 3270 and X emulators.
The network connectivity of the Windows Client also provides
the user access to a full range of network resources.
*************************************************************
Slide 6: Trends
Some customers have asked me "if the Windows Client's
architecture solves such significant problems, why isn't this
technology pervasive?" There have been a number of factors,
primarily technology related, that have represented barriers
to implementing this kind of solution in the past. Only
recently have there been the technology changes necessary to
support this kind of implementation.
From the network perspective, performance has improved
steadily to the point where disk I/O over the LAN is now fast
enough for a diskless client to be feasible. Some of the
networking technology improvements include implementation of
16 bit bus mastering LAN interfaces and performance
improvements to the network operating system. Additionally,
network utilization and penetration has increased
dramatically making a network focused product possible.
Applications have also changed to better support this
technology. They are now more network aware making
management of PC applications easier. Most applications can
now be installed in a shared directory on a server where they
can be accessed by many users, thereby creating economies and
management efficiencies. Applications also have begun to
integrate network smart installation and upgrade procedures.
Finally, the client hardware platform has also evolved to
better support this kind of solution. The ability to fully
integrate LAN, video, and other I/O subsystems has made it
possible to implement a single board design. These hardware
advances have given the Windows Client performance advantages
as well as a very low price point.
The real bottom line here is that the time for the HP
Windows Client is now.
*************************************************************
Slide 7: Networking Environment
We've established that the Windows Client is network focused
with many network performance features built in. Since the
Windows Client requires a LAN environment, let's take a look
at some of the requirements and attributes of such an
environment and how the Windows Client fits in.
Slide 8: Network Environment
The Windows Client has been designed to work with Ethernet
LANs. The network operating systems (N.O.S.) we are
supporting initially are Novell NetWare and LAN Manager.
NetWare is supported running on either the HP 3000 platform
under MPE/iX or HP 9000 platform under HP/UX. It is also
supported running as the native operating system on the Intel
platform.
OS/2 LAN Manager will be supported in October '93 as a boot
server as well as file server. An HP 9000 running LM/X in
such a network will be supported for file server and
application server functions at that time. Diskless boot
from an LM/X server will be supported in second quarter '94.
The final components of the operating environment for the
Windows Client are MS-DOS 6.0 and Windows 3.1.
HP is investigating future support of other networking
environments. We would value your feedback regarding your
needs and priorities.
*************************************************************
Slide 9: Diskless Operation
While some PCs are available with no hard disk, this
structure has been primarily to facilitate adding in third
party drives. There are no other major PC vendors with
products specifically designed and streamlined to function in
a diskless mode, as the Windows Client has been. Let's take
a look, for a minute, at the basis of how diskless operation
works.
When a disk based PC is powered up, something called a "boot-
ROM" looks to a specific sector and track of a local disk
starting with logical drive "A" then "B" then "C" and so
forth until it finds the operating system files. These are
simply program files that are loaded into memory and begin to
execute.
In the Windows Client the boot-ROM is network smart. Instead
of looking for a local mass storage device, it formats a
request and puts it out on the network interface. Any server
configured to respond can provide the necessary files through
something called a boot image. These files are passed
through the network and loaded into memory in exactly the
same way as in the case of the disked PC.
The best way to understand the server based storage utilized
by the Windows Client is to think of it in the same way as a
disked PC with the disk physically located externally across
the LAN. Any time a local application makes a call to disk,
the network operating system intercepts the call and routes
it to the appropriate network disk. This function is
completely transparent to applications and the user.
*************************************************************
Slide 10: Software Installation Process
Because the Windows Client loads DOS, Windows, and PC
applications from the server disk, a software installation
process such as the one pictured in this graphic is used.
Software comes in the traditional floppy disk format and is
loaded onto the server through a disked PC, typically in the
system administration area. The Server Kit is a key part of
this process.
Each Windows Client comes with licenses to use DOS, Windows,
and Reflection Software. The Server Kit provides an
additional license for each of these packages for use on a
disked PC. Bundled with the Server Kit is the media
(5 1/4" and 3 1/2: floppies) for loading the software onto
the network, the full software documentation, as well as a
Basic Support Service.
Also included within the Server Kit are installation
instructions, pre-defined boot images, and all of the drivers
necessary to support HP supplied monitors. Customers using a
third-party monitor, keyboard, or mouse may require
specialized drivers from the third-party supplier.
Note, also, that the value of the Server Kit is further
enhanced by the fact that only one is required per site
regardless of the number of Windows Clients.
"Shrink Wrapped" PC applications, or applications purchased
separately through retailers or other channels, would be
loaded onto the server via the same mechanism as the Windows
Client bundled applications.
*************************************************************
Slide 11: Single Server Configuration
Depending on the attributes of the environment, users will be
implementing either a single server or multiple server
configuration.
In a single server environment, one machine will be serving a
variety of functions. The standard server functions include
providing server application access and file/database access.
Incremental functions the server will provide include the
boot function for the Windows Client as well as the source
for application loading. In a Windows environment, if there
isn't enough memory to hold all of the program information,
the Windows memory manager will swap blocks of information
back and forth to disk. In this single server environment,
the server disk would serve that function. NOTE: it is best
to configure the Windows Client with sufficient memory to
avoid swapping. This can significantly improve performance.
Once the Windows Client has booted and loaded applications,
it will perform in the same way as a disked PC on a network
when accessing server-based applications and databases. File
and database activity related to PC applications will go
across the network to the server as well.
An example of this kind of environment might be an HP 9000 or
HP 3000 running a database application with portable NetWare
to boot the Windows Clients and acting as the PC file server.
*************************************************************
Slide 12: Multiple Server Configuration
A multiple server configuration allows specialization of the
server functions. Here, you can add a focused server,
typically an Intel based server running native NetWare, to
provide the boot and PC file functions. This example could
extend to having several application servers for large or
complex environments. Isolating applications and functions
creates a modularity that can enhance manageability and
optimize performance.
*************************************************************
Slide 13: Key Benefits
So far, we've reviewed the business and technology trends,
looked at the Windows Client attributes, and the networking
requirements of the Windows Client.
Now, we'll examine the ways that the product and environment
attributes of the Windows Client translate into a better
solution. As we go through this, we'll look at the Windows
Client from both the user's perspective and from the
viewpoint of system management.
*************************************************************
Slide 14: Superior Terminal Environment
For terminal users, Windows Client is a superior solution.
By bringing Microsoft Windows into the terminal environment,
users can begin to use the most widely adopted graphical user
interface available. This will add the advantages of a
common look and feel across all of the applications on a
users desktop. Training will be easier and productivity will
improve.
Because the terminal functionality is implemented in
software, multiple emulation modes are available on a single
hardware platform. The Windows Client allows users to run
several concurrent sessions on the same host as well as
provides simultaneous access to multiple hosts.
The ability for users to go beyond the standard terminal
functions and run PC based personal productivity applications
gives the Windows Client a real edge over a traditional
terminal solution. Most terminal users can take immediate
advantage of the additional functionality and there's plenty
of room for growth.
The combination of network access to multiple information
sources and windowing capability between them adds a new
degree of information integration. Now, users can look at
information from two different sources simultaneously and
even cut and paste between them.
Unlike terminals which typically come in only one display
size and resolution, the Windows Client offers a wide range
of monitor choices from monochrome to several different color
solutions. Users can have their choice of screen size and
resolution without sacrificing ergonomics.
Finally, the Windows Client's single board, low power design
allow it to be convection cooled so there is no fan. This
allows users who are used to the silent operation of
terminals to retain that benefit as they move to a
DOS/Windows environment.
*************************************************************
Slide 15: Worry-Free PC Environment
Looking at the Windows Client from the PC users perspective,
it is more worry-free than a traditional PC solution.
Built into the Windows Client is the power and performance
required to meet users needs. The 25 MHz 486 processor is
the mainstream processor platform for the desktop today.
The integrated local-bus video subsystem provides a faster
and wider data path for improved video performance. Terminal
applications as well as word processing and spreadsheet
applications will be able to take advantage of the text
acceleration implemented through color expansion.
Network performance is enhanced through the implementation of
the integrated 16-bit bus mastering LAN interface.
Since the mass storage is server based, the user no longer
has to worry about local hard disk failure and the
corresponding productivity loss. Disk growth needs are
managed at the system level so there is never a need to worry
about upgrading the local disk. Finally, the demand on the
user to perform regular back-ups, something few users do
anyway, is completely eliminated since the server disk is
backed up by the system administrator.
Centralizing the applications on the server actually makes
access easier while providing for control and management.
When a user needs access to a PC application that already
resides on the server, system administration can easily
provide access eliminating the need to first install the
software on a local hard disk. The same advantages carry
over to software upgrades.
Another software worry that users will be free from is the
problem of incompatible software revisions. Version changes
of software can be pretested by MIS to insure new
applications and upgrades are compatible with the overall
environment.
Because it is network based, the Windows Client has the
network advantages of easy file sharing among users,
especially through shared directories.
*************************************************************
Slide 16: Simpler Software Management
Now, let's look at the benefits from a system management
perspective.
By centralizing the PC software onto the server, a consistent
software environment can be created. Whenever an application
upgrade is implemented, all of the users get it at the same
time. By facilitating information exchange between users and
making the environment more easy to manage, support costs go
down and productivity goes up.
With server based disks, software installation and upgrade is
managed by the system administrator rather than the user.
This allows software to be installed once for the benefit of
many users creating time efficiencies. It also insures that
applications are installed and configured properly for
maximum performance and usability.
Central software license management is a significant benefit
of the Windows Client environment. Site license solutions
are much easier to manage and license records are more easily
maintained making software upgrades easier to execute.
Auditing becomes a simple matter since the number of actual
copies of the code is reduced and controlled. The absence of
a local floppy drive also prevents users from installing
unauthorized copies of software on the server.
*************************************************************
Slide 17: Data Integrity and Security
Server based disks allow for data center disk management.
This greatly increases the integrity of the data and
applications. Local hard disks represent a leading source of
failure in PC environments, yet most PCs contain critical
information. When a PC disk fails, valuable data gets lost
and time is wasted rebuilding the environment. Server based
disks allow for fast and reliable back up.
Disk mirroring, RAID technologies, and other high
availability strategies can also be employed where extra data
integrity or data availability is required.
The Windows Client offers numerous benefits from a security
perspective. In fact, this is where the absence of a floppy
drive becomes a real asset. Users are unable to introduce
viruses through floppy disks, which are a leading source of
viruses, and are also unable to download sensitive data for
unauthorized removal. Additional security is provided by the
ability to physically disable the parallel and serial ports.
Password protection is possible at the client and network
level. At the client level, the set-up screen can be
password protected. From a network perspective, a network
login password can be used to prevent access to applications,
data, or network resources until the correct password is
entered. Access permission to applications and data may also
be defined by the system administrator.
Finally, physical security of the Windows Client is provided
through a locking ring on the chassis which prohibits
internal access to the Windows Client as well as allows it to
be secured to a desk or wall.
*************************************************************
Slide 18: Disk Space Savings
Server disks employed by the Windows Client result in
significant disk space savings over a traditional disked PC
solution.
Most disk space in PCs is consumed by applications which are
growing bigger and bigger as they become more sophisticated.
In a disked PC environment, each user must have their own
copy of the software code. In our 20 user example, we are
assuming that the average user will consume roughly 80 Mb of
disk space for DOS, Windows, and applications. This results
in disk space consumption of 1,600 Mb just for the operating
system and applications programs.
The same 20 users will only consume 80 Mb in a server based
disk environment since they will all access the same copy of
the code through shared directories.
The amount of data should stay roughly the same in each
scenario, in this case 400 Mb.
Finally, most PCs are purchased with significantly more disk
space that originally required. We refer to this as "buffer"
space. This is done because upgrading local hard disks that
run out of room is expensive and complex for the average
user. This is really a "buy more than you think you'll need"
kind of mentality.
Buffer space is not required when using a server based disk
since disk growth can be managed and new disk space can be
planned for and implemented on an organizational basis. This
allows disk space to be purchased only when it is needed.
The total benefit of implementing a server based disk
strategy is a 5X reduction in the amount of disk space
required to support the 20 users described in this example.
*************************************************************
Slide 19: Low Cost, Reliable Design
The Windows Client employs a single board design that
integrates the video and LAN interface. The VLSI
construction yields a lower parts count and there are no
connectors for I/O boards or disks so the only connectors
internal to the Windows Client are the two SIMM slots for
memory expansion.
By moving the disk out of the Windows Client and onto the
server, there are no moving parts, the most common cause of
failure. The Windows Client is convection cooled so it
doesn't even need a fan.
Without a disk drive and with the absence of power consuming
interface cards, the Windows Client is a very low power
device. It is rated at only 25 Watts maximum which meets EPA
Energy Star requirements. Typical operation is actually only
about 18 Watts for the system, leading to a measurable
savings in operation cost.
The simplicity of the Windows Client design extends to the
engineering of the chassis and cover. The cover can be
removed in just a few seconds with no tools at all. The
power supply must be disconnected to remove the cover for an
extra measure of safety and the use of the same power module
as the Deskjet printers means there is no high voltage inside
the case.
The simplicity of the design makes the Windows Client a very
low cost solution compared with a disked PC. By eliminating
moving parts, connectors, additional boards, and the heat of
high power devices, reliability is very high. In fact,
reliability is expected to be much better than PCs and
similar to our terminals, which lead the industry in
reliability.
*************************************************************
Slide 20: Model 425SX List Price Comparison
This comparison looks at the list price of a Windows Client
with an entry level color VGA monitor versus several PCs from
reputable manufacturers including HP, Compaq, IBM, DELL and
Northgate.
The desktop configurations are equally configured to include
all of the same components:
4 Mb RAM
Local-bus Ultra VGA video
16-bit LAN interface
DOS/Windows
Color VGA monitor
Mouse and keyboard
It is assumed that networking software and a terminal
emulator will be required. Reflection 2 for Windows and
Reflection Network Series from WRQ come standard with the
Windows Client and have been added in to the cost of the
other PCs. If Reflection 1 for Windows were required (as in
the case of 3000 block-mode applications) $100 would need to
be added to all the numbers shown except for the Windows
Client making the price gap even wider.
The Windows Client comes in 40 percent lower than comparably
configured PCs. When you take into account discounting
practices, all of the prices drop but the same basic
relationship remains.
NOTE: IF ASKED... The cost of server resources on a per user
basis ($50-$200) incurred by the Windows Client is easily
offset by the value of the software licenses for the system
administrator and other cost savings of the environment.
*************************************************************
Slide 21: Model 425SX U.S. List Prices
*************************************************************
Slide 22: Model 425SX U.S.. List Prices (continued)